…ough

A full run over the freshly-filled file lists reported two cases still
opening prose they do not declare: implementation-picks-first-task reads
invoke-skill.md, and discovery-commits-new-epic reads resume-detection.md.

Both were measured clean during the harvest, by a walk that genuinely did
not open them. The harvest walked each case once, and once is a sample: a
walk touches a slightly different set of files each time it runs, so a
single measurement floors the answer rather than settling it.

That is worth knowing about the mechanism itself. A file list converges
across runs rather than being audited in one pass, and the lint is the
ratchet that closes the gap each time a new file surfaces — not a
one-shot check that can be declared finished.

The implementation case is the sharper illustration. During the harvest
its walker claimed to have read invoke-skill.md, the record showed it had
not, and the divergence was recorded as a walker misreporting itself. It
was — and the file it invented reading is genuinely on the path, which
the next run took. A false claim landed on a true fact.

invoke-skill.md is now declared by all four entry cases, which is what
the path shape always implied: it is where every entry skill builds its
handoff.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Every case so far stops where a skill hands off, which is where the phase
begins doing work. Seven processing skills had no coverage at all. This
carries on through the handoff into workflow-investigation-process and
stops at that phase's durability boundary: the file created, the topic
registered, the commit landed, immediately before the symptom interview.

The spine is an ordering claim that crosses the skill boundary — the
entry's status check must precede the processing skill's topic start,
because a topic cannot be started before anything has looked to see
whether it already exists. Alongside it, initialisation must read the
work's seed before writing: the prose opens the phase from the work's
origin, and a walk that wrote first would build the file from nothing.

Scoped to Steps 0 through 2 after reading Step 3, which is a question
bank rather than a gate — Core, Reproduction, Environment, Impact,
Follow-up. That is the organic loop `conduct` is for, and it is better to
shape that field against a case that demands it than to guess now.

Passed first run: 5/5 with the further claim, all four checks, world
matched, and no undeclared prose — the file list was right without a
harvest pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>